Skip to content

Go1.26 goroutine leak#1750

Merged
ma91n merged 1 commit into
mainfrom
feature
Jan 28, 2026
Merged

Go1.26 goroutine leak#1750
ma91n merged 1 commit into
mainfrom
feature

Conversation

@ma91n
Copy link
Copy Markdown
Collaborator

@ma91n ma91n commented Jan 28, 2026

No description provided.

@ma91n ma91n self-assigned this Jan 28, 2026

なお、このアプローチは「検知されたものは確実にリークである(偽陽性が出ない)」ことを重視しており、逆に「リークしているけど検知できない(偽陰性)」ケースはあり得るとされています。

> The advantage of this approach over other goroutine leak detection techniques is that it can be leveraged, with a minimal performance cost, in regular Go systems, e.g., production services. It is also theoretically sound, i.e., there are no false positives. Its primary limitation is that its effectiveness is reduced the more heap resources are over-exposed in memory, i.e., pair-wise reachable.
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🚫 [textlint] <eslint.rules.ja-technical-writing/max-comma> reported by reviewdog 🐶
This sentence exceeds the maximum count of comma. Maximum is 3. (ja-technical-writing/max-comma)

@ma91n ma91n merged commit 5e5ec1b into main Jan 28, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant